Pointing "File History" to a NAS causes services to crash

First of all, I have no idea if I'm posting this to the right forum. If I am not, I am sorry. I just felt that I had to share what I've noticed.

I'm running Windows 8.1 preview on my machine and I've been having some troubles with my Wi-Fi loosing connection all of a sudden. When I checked the event it log told me that the WLAN AutoConfig service crashed unexpectedly (code 1067, which basically tells me nothing).

After some digging through the logs it seems like the File History Service is what causing this. I have my File History pointed to a Apple Time Capsule so that I know that my files are always safe. The Time Capsule has a tendency to put the hard drive in sleep mode every 2 seconds and what I think happens is that when it takes too long for the drive to spin up again, the File History service crashes.

The thing that made me come to this conclusion is that when the File History service crashes, so does the WLAN AutoConfig service (and a whole bunch of other services), at the exact same moment. Here is a list of the services which crashes along with the File History service:

  • Windows Driver Foundation - User-mode Driver Framework 
  • WLAN AutoConfig 
  • Diagnostic System Host 
  • Distributed Link Tracking Client 
  • Superfetch
  • Program Compatibility Assistant Service 
  • Network Connections 
  • Network Connection Broker 
  • HomeGroup Listener 
  • Human Interface Device Service 
  • File History Service 
  • Device Association Service 
  • Offline Files 
  • Windows Audio Endpoint Builder 

I'm using Dropbox to keep my files safe now instead so it's no biggie at all, just thought I'd share.

My log is all in Swedish, but if it would help in some way, I can of course post it.


July 8th, 2013 7:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics